Preview deployment for your docs. Learn more about Mintlify Previews.

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
grid-flow-builder	Ready	Preview, Comment	May 25, 2026 11:34am

@greptile review

Greptile Summary

This PR syncs eleven onboarding/KYC documentation files with the current OpenAPI schema, correcting invented webhook event names, deprecated field shapes, and stale enum values across all four product verticals (global-p2p, payouts-and-b2b, ramps, rewards).

• Webhook event types corrected from invented names (KYC_STATUS, INVITATION_CLAIMED) to schema-accurate dot-notation (CUSTOMER.KYC_APPROVED, CUSTOMER.KYC_REJECTED, CUSTOMER.KYC_PENDING, and CUSTOMER.KYB_* siblings); example handler in kyc-webhooks.mdx now includes all six cases and the stale "only final states" comment is replaced.
• Request body shapes updated: POST /beneficial-owners now uses roles[] + nested personalInfo; POST /documents uses documentHolder + country; business customer create/PATCH uses businessInfo.{legalName, taxId}; bulk CSV columns and job-status response match the BulkCustomerImportErrorEntry schema.
• kycStatus enum trimmed to the terminal set APPROVED | REJECTED; EXPIRED, CANCELED, and MANUALLY_* variants removed from all docs.

Confidence Score: 4/5

Safe to merge with one prose fix in the KYB document upload step before publishing.

The KYB 'Upload supporting documents' step in kyc-unregulated.mdx still describes the old customerId and beneficialOwnerId form fields in its prose, while the code example below it already uses documentHolder. A developer following the text description will pass the wrong field names to the API. Everything else — event types, payload shapes, enum values, CSV schema — is cleanly updated.

mintlify/snippets/kyc/kyc-unregulated.mdx — the KYB document upload prose (around line 257) uses stale form field names that contradict the corrected code example.

sequenceDiagram
    participant P as Platform
    participant G as Grid API
    participant W as Webhook Endpoint

    P->>G: POST /customers (customerType + info)
    G-->>P: "{ id, kycStatus: PENDING }"

    alt Hosted flow
        P->>G: "POST /customers/{id}/kyc-link"
        G-->>P: "{ kycUrl, token, expiresAt }"
        P->>P: Redirect customer to kycUrl
    else Direct API (KYC)
        P->>G: POST /documents (documentHolder, country, file)
        P->>G: "POST /verifications { customerId }"
    else Direct API (KYB)
        P->>G: POST /beneficial-owners (roles[], personalInfo)
        P->>G: POST /documents (documentHolder, country, file)
        P->>G: "POST /verifications { customerId }"
    end

    G->>W: CUSTOMER.KYC_PENDING (intermediate)
    G->>W: CUSTOMER.KYC_APPROVED or CUSTOMER.KYC_REJECTED (terminal)
    Note over G,W: Business customers emit KYB_* siblings

    W->>P: Activate or reject customer

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
mintlify/snippets/kyc/kyc-unregulated.mdx:257
**Stale field names in KYB document upload prose**

This sentence still refers to `customerId` and `beneficialOwnerId` as the form fields to use, but this PR changed both to the unified `documentHolder` field. A developer reading this description will attempt `-F "customerId=..."` and `-F "beneficialOwnerId=..."`, which no longer match the API — the code example immediately below uses `-F "documentHolder=..."` for the beneficial owner case, while the business customer case (referencing a `Customer:...` ID) isn't shown at all for KYB. The prose and code examples are now in direct conflict.

### Issue 2 of 2
mintlify/snippets/creating-customers/customers.mdx:311-312
**Stale error example references removed bank-account concept**

The sample error message says "Invalid bank account number" but this PR explicitly removed all bank-account columns from the bulk CSV format with the note that bank accounts are now managed separately via `/customers/external-accounts`. Using a bank-account error as the illustrative example in the same block that just removed bank-account columns will confuse developers who expect a representative error for the new schema. The same stale example appears in `global-p2p/onboarding/configuring-customers.mdx` and `payouts-and-b2b/onboarding/configuring-customers.mdx`.

_{Reviews (4): Last reviewed commit: "add KYB_* cases to webhook handler examp..." | Re-trigger Greptile}

@greptile review

@greptile review